`peckingorder.co`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:1a9c^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::ac43:8922^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.26.156^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.137.34^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ajay.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b38^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ajay.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c138^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ajay.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2138^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ajay.ns.cloudflare.com`
		A	108.162.193.56^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ajay.ns.cloudflare.com`
		A	172.64.33.56^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ajay.ns.cloudflare.com`
		A	173.245.59.56^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ajay.ns.cloudflare.com`
NS	`zoe.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a95^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c095^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`zoe.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2095^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`zoe.ns.cloudflare.com`
		A	108.162.192.149^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	172.64.32.149^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	173.245.58.149^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁴⁰⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁶⁰⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.26.156, 172.67.137.34
		IPv6 hints	2606:4700:3030::6815:1a9c, 2606:4700:3032::ac43:8922
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=73, name=cloudflare-ech.com
SOA	`ajay.ns.cloudflare.com`dns@cloudflare.com serial=2400200838

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759632151

Same first word

peckingorder.co

DNS History

9 records (9 active, 0 former)

●NSajay.ns.cloudflare.com2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●NSzoe.ns.cloudflare.com2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●MXroute1.mx.cloudflare.net2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●MXroute2.mx.cloudflare.net2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●MXroute3.mx.cloudflare.net2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●A104.21.26.1562026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●A172.67.137.342026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●A2606:4700:3030::6815:1a9c2026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

●A2606:4700:3032::ac43:89222026-04-02 → 2026-04-12 · 2 obs

● 2026-04-02 20:14:26
● 2026-04-12 09:20:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	-
peckingorder.co	zoe.ns.cloudflare.com, ajay.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.149

NS records: zoe.ns.cloudflare.com, ajay.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for peckingorder.co (unsigned zone)

⏱️ Timing

Total: 280ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.26.156, 172.67.137.34`
AAAA	2	`2606:4700:3030::6815:1a9c, 2606:4700:3032::ac43:8922`
NS	2	`ajay.ns.cloudflare.com, zoe.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 28), route3.mx.cloudflare.net (pri: 40)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ajay.ns.cloudflare.com dns.cloudflare.co`

Analysis

IP Addresses

peckingorder.co refers to four IP numbers: 2606:4700:3030::6815:1a9c, 2606:4700:3032::ac43:8922, 104.21.26.156 and 172.67.137.34.

Other host names, for instance cpanel.mvdagenciademedios.com.ar, book-of-ra-classic.com, www.djclub.net, niikaplayerr.com and fpggg.com share IP numbers with peckingorder.co.

Name Servers

peckingorder.co's delegation uses two name servers: ajay.ns.cloudflare.com and zoe.ns.cloudflare.com.

peckingorder.co uses the same name server setup as other domains, such as signsetc.com.au, myfoliahealth.com, cullens.co.uk, dougiehunt.com and gosurrey.co.uk.

peckingorder.co at least partially shares name servers with other domains, including adnan.eu, xx613.com, directcbd.com, voicesforprogress.org and macrosynergypattern.click.

These name servers are commonly used with paityn.ns.cloudflare.com, aiden.ns.cloudflare.com and olivia.ns.cloudflare.com.

Host names with six IP numbers:

ajay.ns.cloudflare.com points to 2606:4700:58::adf5:3b38, 2803:f800:50::6ca2:c138, 2a06:98c1:50::ac40:2138, 108.162.193.56, 172.64.33.56 and 173.245.59.56.

zoe.ns.cloudflare.com points to 2606:4700:50::adf5:3a95, 2803:f800:50::6ca2:c095, 2a06:98c1:50::ac40:2095, 108.162.192.149, 172.64.32.149 and 173.245.58.149.

Mail Servers

Three mail servers handle peckingorder.co: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

peckingorder.co shares at least some mail servers with other domains, for example effortis.com, effem-equine.com, totogamingcasino.top, nsfw.host and leadliftlab.com.

Host names with six IP numbers:

route1.mx.cloudflare.net points to: 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13

route2.mx.cloudflare.net points to: 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19

route3.mx.cloudflare.net points to: 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25

peckingorder.co - robtex.com

peckingorder.co

co

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`peckingorder.co`

`co`