middaybreak.com - dns.ninja

`middaybreak.com`

DNSSEC	⚠️ Not signed
A	64.190.63.222^{🇩🇪 SEDO64.190.62.0/23 -NET2-PI}
NS	`ns1.sedoparking.com` ⭐
		A	3.130.216.63^{🇺🇸 Amazon3.130.0.0/16 EC2 CMH prefix}
			PTR	`ec2-3-130-216-63.us-east-2.compute.amazonaws.com`
		A	91.195.241.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
NS	`ns2.sedoparking.com`
		A	34.211.188.210^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
			PTR	`ec2-34-211-188-210.us-west-2.compute.amazonaws.com`
		A	91.195.240.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
MX	`localhost` ⭐
TXT	`v=spf1 -all`
SOA	`ns1.sedoparking.com`hostmaster@sedo.de 2018-05-16 #1

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1786266889

Same first word

middaybreak.com

DNS History

23 records (4 active, 19 former)

○NSbuy.internettraffic.com2015-07-06 → 2016-04-12 · 4 obs

● 2015-07-06 02:16:44
● 2016-04-12 20:32:28
○ 2016-12-29 00:34:20
○ 2026-08-09 09:25:44

○NSjiaoqing.ns.giantpanda.com2026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○NSns1.bodis.com2026-04-13 → 2026-08-09 · 2 obs

○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

●NSns1.sedoparking.com2026-07-08 → 2026-08-09 · 3 obs

○ 2026-04-13 13:56:00
● 2026-07-08 05:49:18
● 2026-08-09 09:25:44

○NSns1.uniregistrymarket.link2016-12-29 → 2018-01-23 · 5 obs

○ 2016-04-12 20:32:28
● 2016-12-29 00:34:20
● 2018-01-23 10:10:22
○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

○NSns2.bodis.com2026-04-13 → 2026-08-09 · 2 obs

○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

●NSns2.sedoparking.com2026-07-08 → 2026-08-09 · 3 obs

○ 2026-04-13 13:56:00
● 2026-07-08 05:49:18
● 2026-08-09 09:25:44

○NSns2.uniregistrymarket.link2016-12-29 → 2018-01-23 · 5 obs

○ 2016-04-12 20:32:28
● 2016-12-29 00:34:20
● 2018-01-23 10:10:22
○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

○NSpo.ns.giantpanda.com2026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○NSsell.internettraffic.com2015-07-06 → 2016-04-12 · 4 obs

● 2015-07-06 02:16:44
● 2016-04-12 20:32:28
○ 2016-12-29 00:34:20
○ 2026-08-09 09:25:44

●MXlocalhost2026-07-08 → 2026-08-09 · 2 obs

● 2026-07-08 05:49:18
● 2026-08-09 09:25:44

○A199.59.243.2282026-04-13 → 2026-08-09 · 2 obs

○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

○A2600:3c03::f03c:95ff:fe00:29ca2026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A2600:3c03::f03c:95ff:fe91:5d522026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A2600:3c03::f03c:95ff:feed:4d4f2026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A2600:3c03::f03c:95ff:feed:cf2a2026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A45.33.83.1002026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A45.79.167.1802026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

●A64.190.63.2222026-07-08 → 2026-08-09 · 3 obs

○ 2026-04-13 13:56:00
● 2026-07-08 05:49:18
● 2026-08-09 09:25:44

○A66.175.209.1792026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

○A69.172.201.1532016-12-29 → 2018-01-23 · 5 obs

○ 2016-04-12 20:32:28
● 2016-12-29 00:34:20
● 2018-01-23 10:10:22
○ 2026-04-13 13:56:00
○ 2026-08-09 09:25:44

○A69.172.201.2082015-07-06 → 2016-04-12 · 4 obs

● 2015-07-06 02:16:44
● 2016-04-12 20:32:28
○ 2016-12-29 00:34:20
○ 2026-08-09 09:25:44

○A96.126.111.1652026-04-13 → 2026-04-13 · 4 obs

○ 2018-01-23 10:10:22
● 2026-04-13 13:56:00
○ 2026-07-08 05:49:18
○ 2026-08-09 09:25:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
middaybreak.com	ns1.sedoparking.com, ns2.sedoparking.com	2 records

✅ Authoritative Response

Server:91.195.240.8

NS records: ns1.sedoparking.com, ns2.sedoparking.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for middaybreak.com (unsigned zone)

⏱️ Timing

Total: 3268ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.190.63.111`
NS	2	`ns1.sedoparking.com, ns2.sedoparking.com`
MX	1	`localhost (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.sedoparking.com hostmaster.sedo.de`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.sedoparking.com, ns2.sedoparking.com)

Analysis

IP Addresses

middaybreak.com points to a single IP number: 64.190.63.222.

Additional host names — fussballmail.de, mx.globalfund.de, sqs.haussolaranlage.de and two others — share IP numbers with middaybreak.com.

Name Servers

middaybreak.com uses two name servers for its delegation: ns1.sedoparking.com and ns2.sedoparking.com.

middaybreak.com shares its name server setup with other domains, including cpape.com, mail.think-simple.com, vibhagalhotra.site and two others.

At least some of middaybreak.com's name servers are also used by other domains, among them fwz.in.

The two host names ns1.sedoparking.com and ns2.sedoparking.com each have a pair of IP addresses: ns1.sedoparking.com has 3.130.216.63 and 91.195.241.8, and ns2.sedoparking.com has 34.211.188.210 and 91.195.240.8.

Mail Servers

middaybreak.com has one mail server: localhost.

middaybreak.com shares the same mail server setup as other domains, including ns1.codalia.com, d31qbv1cthcecs.cloudfront.ne, chalena.com and two others.