sqlblog.nl - dns.ninja

`sqlblog.nl`

DNSSEC	⚠️ Not signed
A	2a07:ae80:100:0:185:158:165:64^{🇳🇱 ATOM86-AS2a07:ae80::/29}
		PTR	`i185-158-165-64.webawere.nl`
		PTR	`linux42.webawere.nl`
A	185.158.165.64^{🇳🇱 ATOM86-AS185.158.164.0/22}
NS	`ns1.webawere.nl` ⭐
		A	2a07:ae80:100:0:185:158:165:26^{🇳🇱 ATOM86-AS2a07:ae80::/29}
			PTR	`ns1.webawere.nl`
		A	185.158.165.26^{🇳🇱 ATOM86-AS185.158.164.0/22}
			PTR	`ns1.webawere.nl`
NS	`ns2.webawere.nl`
		A	2a00:1188:5:7:95:142:98:222^{🇳🇱 ATOM86-AS2a00:1188::/29 ATOM86 IPv6 Route object}
			PTR	`ns2.webawere.nl`
		A	95.142.98.222^{🇳🇱 ATOM86-AS95.142.96.0/20 ATOM86 Route object}
			PTR	`ns2.webawere.nl`
MX	`linux2027.webawere.nl` ⭐
		A	2a07:ae80:100:0:185:158:164:73^{🇳🇱 ATOM86-AS2a07:ae80::/29}
			PTR	`linux2027.webawere.nl`
		A	185.158.164.73^{🇳🇱 ATOM86-AS185.158.164.0/22}
			PTR	`linux2027.webawere.nl`
TXT	`v=spf1 a mx include:webawere.nl ~all`
SOA	`ns1.webawere.nl`hostmaster@sqlblog.nl 2026-08-01 #1

`nl`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns1.dns.nl` ⭐
	NS	`ns3.dns.nl`
	NS	`ns4.dns.nl`
	TXT	`nl zone update: 2026-08-10 05:30:02 +0000 (EPOCH 1786339802)`
	SOA	`ns1.dns.nl`dns@sidn.nl 2026-08-10 #11

Same first word

sqlblog.nl

sqlblog.com

sqlblog.cn

sqlblog.eu

DNS History

8 records (5 active, 3 former)

●NSns1.webawere.nl2015-06-28 → 2026-08-10 · 2 obs

● 2015-06-28 20:55:28
● 2026-08-10 06:31:22

●NSns2.webawere.nl2015-06-28 → 2026-08-10 · 2 obs

● 2015-06-28 20:55:28
● 2026-08-10 06:31:22

●MXlinux2027.webawere.nl2026-02-18 → 2026-08-10 · 3 obs

○ 2018-08-13 10:36:12
● 2026-02-18 19:26:20
● 2026-08-10 06:31:22

○MXmail.sqlblog.nl2015-06-28 → 2018-08-13 · 4 obs

● 2015-06-28 20:55:28
● 2018-08-13 10:36:12
○ 2026-02-18 19:26:20
○ 2026-08-10 06:31:22

○MXnolisting.webawere.nl2015-06-28 → 2017-01-01 · 4 obs

● 2015-06-28 20:55:28
● 2017-01-01 09:50:24
○ 2018-08-13 10:36:12
○ 2026-08-10 06:31:22

●A185.158.165.642018-08-13 → 2026-08-10 · 3 obs

○ 2017-01-01 09:50:24
● 2018-08-13 10:36:12
● 2026-08-10 06:31:22

●A2a07:ae80:100:0:185:158:165:642018-08-13 → 2026-08-10 · 3 obs

○ 2017-01-01 09:50:24
● 2018-08-13 10:36:12
● 2026-08-10 06:31:22

○A83.96.159.642015-06-28 → 2017-01-01 · 4 obs

● 2015-06-28 20:55:28
● 2017-01-01 09:50:24
○ 2018-08-13 10:36:12
○ 2026-08-10 06:31:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
nl	ns1.dns.nl, ns3.dns.nl, ns4.dns.nl	-
sqlblog.nl	ns1.webawere.nl, ns2.webawere.nl	4 records

✅ Authoritative Response

Server:185.158.165.26

NS records: ns1.webawere.nl, ns2.webawere.nl

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sqlblog.nl (unsigned zone)

⏱️ Timing

Total: 305ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.158.165.64`
AAAA	1	`2a07:ae80:100:0:185:158:165:64`
NS	2	`ns1.webawere.nl, ns2.webawere.nl`
MX	2	`linux2027.webawere.nl (pri: 10), linux2027.webawere.nl (pri: 30)`
TXT	1	`v=spf1 a mx include:webawere.nl ~all`
SOA	1	`ns1.webawere.nl hostmaster.sqlblog.nl`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.webawere.nl, ns2.webawere.nl, ns1.webawere.nl...)

Analysis

IP Addresses

sqlblog.nl directs to two IP numbers, 185.158.165.64 and 2a07:ae80:100:0:185:158:165:64

concinnitas.org, sgwww.goededoelenkaartje.nl, com.sgwww.goededoelenkaartje.nl plus two other host names have IP numbers in common with sqlblog.nl.

Name Servers

sqlblog.nl is delegated to two name servers: ns1.webawere.nl and ns2.webawere.nl.

The name server configuration of sqlblog.nl is shared with other domains, for instance musicad.nl, canvastix.be, quodest.com and two others.

sqlblog.nl partially shares its name servers with domains like shoox.nl and suit4sale.nl.

ns1.webawere.nl and ns2.webawere.nl each resolve to two IP addresses: ns1.webawere.nl points to 185.158.165.26 and 2a07:ae80:100:0:185:158:165:26, while ns2.webawere.nl points to 95.142.98.222 and 2a00:1188:5:7:95:142:98:222.

Mail Servers

sqlblog.nl uses one mail server — linux2027.webawere.nl.

The mail server setup of sqlblog.nl matches that of other domains such as alkmaardermeer.nl, tr2.it, kapsalonageeth.nl and two others.

The host linux2027.webawere.nl resolves to 185.158.164.73 and 2a07:ae80:100:0:185:158:164:73 — two IP addresses.