whmcr / WHMCR

Robots.txt Information

Robot	Path	Permission
GoogleBot	/	✔
BingBot	/	✔
BaiduSpider	/	✔
YandexBot	/	✔
User-agent: * Allow: / Sitemap:

Meta Tags

Title	WHMCR
Description	Welby ↓ Welby McRoberts WHMCR - Random Mutterings Blog Tags Old Content Forcing A or AAAA record resolution with CoreDNS 6 November 2022 · 690 words · 4 mins In
Keywords	N/A

Server Information

WebSite	whmcr.com
Host IP	104.21.1.174
Location	United States

Related Websites

                        Site
                        Rank
                    

More to Explore

whmcr.com Valuation

US$330,531

Last updated: 2023-05-12 11:46:01

whmcr.com has Semrush global rank of 32,022,161. whmcr.com has an estimated worth of US$ 330,531, based on its estimated Ads revenue. whmcr.com receives approximately 38,139 unique visitors each day. Its web server is located in United States, with IP address 104.21.1.174. According to SiteAdvisor, whmcr.com is safe to visit.

Traffic & Worth Estimates

Purchase/Sale Value	US$330,531
Daily Ads Revenue	US$306
Monthly Ads Revenue	US$9,154
Yearly Ads Revenue	US$109,838
Daily Unique Visitors	2,543
Note: All traffic and earnings values are estimates.

DNS Records

Host	Type	TTL	Data
whmcr.com.	A	299	IP: 104.21.1.174
whmcr.com.	A	299	IP: 172.67.129.170
whmcr.com.	AAAA	299	IPV6: 2606:4700:3035::6815:1ae
whmcr.com.	AAAA	299	IPV6: 2606:4700:3030::ac43:81aa
whmcr.com.	NS	86400	NS Record: ray.ns.cloudflare.com.
whmcr.com.	NS	86400	NS Record: elsa.ns.cloudflare.com.
whmcr.com.	MX	300	MX Record: 5 alt2.aspmx.l.google.com.
whmcr.com.	MX	300	MX Record: 10 alt3.aspmx.l.google.com.
whmcr.com.	MX	300	MX Record: 10 alt4.aspmx.l.google.com.
whmcr.com.	MX	300	MX Record: 1 aspmx.l.google.com.
whmcr.com.	MX	300	MX Record: 5 alt1.aspmx.l.google.com.
whmcr.com.	TXT	300	TXT Record: keybase-site-verification=qC4V1oyQfAmojEgDPUxRoNwp9J4Pux7sNmVRh5RLbiE
whmcr.com.	TXT	300	TXT Record: v=spf1 mx a include:mailgun.org include:_spf.google.com ~all
whmcr.com.	TXT	300	TXT Record: google-site-verification=bhI2e_hB1v5d-O2MIY_b2wqRpv-K2R-fZfUsv92V-W8
whmcr.com.	TXT	300	TXT Record: google-site-verification=hk8c8KD4F7bTX-EdotDCSKlsUQAiExbtwGXsBwZJfes

HtmlToTextCheckTime:2023-05-12 11:46:01

↓ Welby McRoberts WHMCR - Random Mutterings Blog Tags Old Content Forcing A or AAAA record resolution with CoreDNS 6 November 2022 · 690 words · 4 mins Infrastructure Networking coredns Linux Some devices will favour IPv6 when configured, which is great, however there are sometimes that you want a device to only resolve either the v4 or v6 addresses. In this case it was for ICMP monitoring of remote devices. The device doing the monitoring will favour IPv6 over IPv4, which is great, however I want to be able to monitor both. CoreDNS is the DNS server which I use for serving up internal DNS, so I was looking for a way to use this to perform the forcing of records. I went back and forth on ways to do this, templates, different forwardings based on domain and so on, however I ended up using the rewrite to acheive this. An example Corefile would be as follows (with my other configuration removed) (bind) { bind 127.0.0.1 bind 127.0.0.53 bind ::1 bind 192.168.1.2 } a:53 { import bind

HTTP Headers

HTTP/1.1 307 Temporary Redirect
Date: Wed, 15 Dec 2021 09:31:01 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 18
Connection: keep-alive
location: https://whmcr.com/
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=2D%2BBy6gCL%2B4Qq8C5sSgZ0wYrd2FSpCOf%2F9JlMdjecLlDiQQGWrBt4Wir1KH9YXpJllFe7i0Vrq17XoAKlUwueWUasymp0mW0CjuTKVpQqrvAEFz6ydLykdF41yw%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 6bdea812dce619c7-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

HTTP/2 200 
date: Wed, 15 Dec 2021 09:31:01 GMT
content-type: text/html; charset=UTF-8
link: ; rel="https://api.w.org/"
x-powered-by: PHP/7.3.14
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=IbRadYHqHdmAZFCExDLj7nkeEmIQ8LDX83YRs1YQETear5RYSKJ8ymo6rX8sGiUA4GSlzfAdVXIEPo8hfjle%2Ba6yX1qrH4DtkbfIaBZrvq4LHdgxlaAaYnsbFQQ%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 6bdea813ec321809-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

whmcr.com Whois Information

Domain Name: WHMCR.COM
Registry Domain ID: 242265589_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2019-04-13T05:11:57Z
Creation Date: 2005-10-29T18:13:21Z
Registry Expiry Date: 2022-10-29T18:13:21Z
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ELSA.NS.CLOUDFLARE.COM
Name Server: RAY.NS.CLOUDFLARE.COM
DNSSEC: signedDelegation
DNSSEC DS Data: 2371 13 2 D25C0228FA49E01F6829CE5FA788639C36474C9D06B20A474737BFED56F3C929
>>> Last update of whois database: 2021-12-15T08:34:27Z <<<

whmcr.com valuation and analysis