antipaucity.com Report : Visit Site

Technical data of the antipaucity.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host antipaucity.com. Currently, hosted in Germany and its service provider is Hetzner Online AG .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.6.37 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

fighting the lack of good ideas extra large large normal about beverages projects stuff support travel finally starting to get some good docs amassed july 28th, 2018 i had a decent library of documentation , templates, hand-offs, slide decks, etc in my pre- splunk consulting life (technically, i still have them). it’s nice to be finally getting a decent collection to draw from for my customers in my post- automation consulting life. posted by under technical , work with no comments tags: documentation , library , splunk you can’t disaggregate july 26th, 2018 had a customer recently ask about to disaggregate a splunk search that had aggregated fields because they export to csv horribly. here’s the thing. you can’t disaggregate aggregated fields. and there’s a good reason™, too: aggregation , by definition, is a one-way street. you can’t un-average something. average is an aggregation function. so why would you think you could disaggregate any other splunk aggregation operation (like values or list )? you can’t. and you shouldn’t be able to (as nice as the theoretical use case for it might be). so what is a body to do when you have a use case for a clean-to-export report that looks as if it had been aggregated, but every field in each row cleanly plunks-out to a single comma-separated value? here’s what i did: {parent search} | join {some field that'll exist in the subsearch} [ search {parent search} | stats {some stats functions here} ] | fields - {whatever you don't want} | sort - {fieldname} what does that end up doing? the subsearch is identical to the outer search, plus whatever filtering/ where /|stats you might want/need to do. using the resultant, filtered set, join on a field you know will be unique [enough]. then sort however you’d like, and remove whatever fields you don’t want in the final display. of course, be sure your subsearch will complete in under 60 seconds and/or return fewer than 10,000 lines (unless you’ve modified your splunk limits.conf ) posted by under insights , technical with no comments tags: aggregator , splunk , stats stats values vs stats list in splunk july 24th, 2018 splunk ’s | stats functions are incredibly useful and powerful. there are two, list and values that look identical…at first blush. but they are subtly different. here’s how they’re not the same. values is an aggregating, uniquifying function. list is an aggregating, not uniquifying function. “whahhuh?!” i hear you ask. here’s a prime example – say you’re aggregating on the field ip_addr all user values. your search might contain the following chunk: | stats values(user) as user by ip_addr . so for each unique ip address, you will collate a uniquified list of users. maybe you have the following two ip addresses: 10.10.10.10 & 10.10.20.10 . and you have the following user-ip address pairings: kingpin11 10.10.10.10 , fergus97 10.10.20.10 , gerfluggle 10.10.10.10 , kingping11 10.10.10.10 , jbobgorry 10.10.10.10 . values will aggregate all of the following users associated with ip addresses: 10.10.10.10 & gerfluggle, jbobgorry, kingping11 ; 10.10.20.10 & fergus97 . that’s nice – it’s pretty. but it exports in lousy form if you need to further process the data in another tool (eg microsoft excel ). when splunk exports those results in a csv, instead of getting a nice, processable file, you get tabs separating what would otherwise be individual items that have all been grouped into one field. enter list . list doesn’t uniquify the values given to it, so while you still only get one line per ip address (since that was our by clause in the snippet above), you get as many ip addresses listed as there are users (in this example). this makes for an exportable, more processable set of results that a tool like excel can ingest to perform further analysis with relatively little reformatting needed. come back tomorrow for how to get the export to work “out of the box”. posted by under technical with no comments tags: splunk about burning bridges july 22nd, 2018 while you should never be the one to burn the bridge of a relationship, sometimes you need to be aware that the other person had placed dynamite around the joints, soaked the whole shebang in gasoline, and is walking around on top with a lit road flare: and you don’t want to be around when the conflagration begins * . * though – sitting far enough away the shards and embers won’t hit you while chant, “burn, baby, burn” can be quite entertaining posted by under insights with no comments tags: advice manning is doing something similar to my bucket proposal july 21st, 2018 manning publishers has a livebook offering. and it allows for the type of mini transactions (through their self-hosted “token” system) that i proposed when writing about how i’d dumped pi-hole last year. quoting from their recent announcement email book publishers follow a simple rule: put your content behind a solid paywall. at manning, we believe you should be able to see before you buy. livebook search and manning tokens make the paywall porous. our new new timed unlock feature moves the whole wall further back! that’s pretty dang cool, manning . posted by under books , cool with no comments tags: books , ebook , microtransactions , paywall never be the one to burn the bridge july 20th, 2018 but always carry a can of gasoline and some matches – because sometimes you do need to be the one to break the relationship. posted by under insights with 1 comment tags: advice a fairly comprehensive squid configuration for proxying all the http things july 18th, 2018 after combing through the docs and several how – tos on deploying the squid proxy server – none of which really did everything i wanted, of course – i’ve finally gotten to the format below. installing squid is easy-peasy – it’s in the standard package repos for the major platforms ( centos / fedora / rhel , ubuntu / debian , etc) – so just run yum install squid or apt install squid on your platform of choice (my exact install command on ubuntu 18.04 was apt -y install squid net-tools apache2-utils ). what i wanted was an “open” (password-protected) proxy server with disk-based caching enabled that would cover all of the ports i could reasonably expect to run into. why “open”? because i want to be able to turn it on and off on various mobile devices which may (or may not) have stable-ish public ips. here is the config as i have it deployed, minus sensitive/site-specific items (usernames, passwords, port, etc), of course: a working /etc/squid/squid.conf acl ssl_ports port 443 acl ssl_ports port 8443 acl safe_ports port 80 # http acl safe_ports port 21 # ftp acl safe_ports port 443 # https acl safe_ports port 1025-65535 # unregistered ports acl safe_ports port 280 # http-mgmt acl safe_ports port 488 # gss-http acl safe_ports port 777 # multiling http acl safe_ports port 8080 acl connect method connect auth_param basic program /usr/lib/squid/basic_ncsa_auth /etc/squid/.htpasswd auth_param basic children 15 # after "realm", put some descriptive, clever, or otherwise-identifying string that will appear when you login auth_param basic realm insert incredibly witty title here auth_param basic credentialsttl 5 hours acl password proxy_auth required http_access allow password # deny requests to certain unsafe ports http_access deny !safe_ports # deny connect to other than secure ssl ports http_access deny connect !ssl_ports # only allow cachemgr access from localhost http_access allow localhost manager http_access deny manager #http_access allow localnet http_access allow localhost # and finally deny all other access to this proxy # commented-out to allow "open" use (ie password authenticated) #http_access deny all # squid normally listens to port 3128 # change this line if you want it to listen on something other port # http_port # uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /var/spool/squid 100 16 256 # format is cache_dir ufs /tmp/squid-cache 768 16

URL analysis for antipaucity.com

https://antipaucity.com/tag/vmware/
https://antipaucity.com/beverages/
https://antipaucity.com/tag/sun-tzu/
https://antipaucity.com/tag/blog/
https://antipaucity.com/2018/07/20/never-be-the-one-to-burn-the-bridge
https://antipaucity.com/category/books/
https://antipaucity.com/tag/data/
https://antipaucity.com/tag/books/
https://antipaucity.com/2018/07/21/manning-is-doing-something-similar-to-my-bucket-proposal/#respond
https://antipaucity.com/tag/twitter/
https://antipaucity.com/2018/07/22/about-burning-bridges/#respond
https://antipaucity.com/2017/08/11/pi-hole-revisited/#.waliphd97go)
https://antipaucity.com/tag/library/
https://antipaucity.com/tag/splunk/
https://antipaucity.com/tag/social-media/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: ANTIPAUCITY.COM
Registry Domain ID: 354070274_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.pairdomains.com
Registrar URL: http://www.pairdomains.com
Updated Date: 2018-03-27T21:59:40Z
Creation Date: 2006-02-22T01:12:10Z
Registry Expiry Date: 2023-02-22T01:12:10Z
Registrar: pair Networks, Inc. d/b/a pair Domains
Registrar IANA ID: 99
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS3.PAIRNIC.COM
Name Server: NS4.PAIRNIC.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-09-05T18:12:37Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR pair Networks, Inc. d/b/a pair Domains

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =antipaucity.com

  PORT 43

  TYPE domain

DOMAIN

  NAME antipaucity.com

  CHANGED 2018-03-27

  CREATED 2006-02-22

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  NS3.PAIRNIC.COM 216.92.3.93

  NS4.PAIRNIC.COM 66.39.7.34

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .