technologypep.com - dns.ninja

`technologypep.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3035::6815:14fd^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:c33f^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.20.253^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.195.63^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ada.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a36^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ada.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c036^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ada.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2036^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ada.ns.cloudflare.com`
		A	108.162.192.54^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ada.ns.cloudflare.com`
		A	172.64.32.54^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ada.ns.cloudflare.com`
		A	173.245.58.54^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ada.ns.cloudflare.com`
NS	`eric.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b70^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eric.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c170^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`eric.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2170^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`eric.ns.cloudflare.com`
		A	108.162.193.112^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eric.ns.cloudflare.com`
		A	172.64.33.112^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eric.ns.cloudflare.com`
		A	173.245.59.112^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eric.ns.cloudflare.com`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`ahrefs-site-verification_be0efdf2f3d9703db7a51e4330c973ff2b07e40dbebe77abfb85...`
TXT	`bm-site-verification=dc6bba7fc45386d4a1bab10fa3c94aa23b75f29b`
TXT	`google-site-verification=qDM_5gOBZcr4PpdhIegrdzeACmdqAWcaf4IdRGLFBpo`
TXT	`v=spf1 redirect=_spf.yandex.net`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.20.253, 172.67.195.63
		IPv6 hints	2606:4700:3035::6815:14fd, 2606:4700:3037::ac43:c33f
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=172, name=cloudflare-ech.com
SOA	`ada.ns.cloudflare.com`dns@cloudflare.com serial=2408741294

`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=1785988714

WOT: SAFE (59/100)

Same first word

technologypep.com

DNS History

18 records (7 active, 11 former)

○NSabby.ns.cloudflare.com2016-03-01 → 2016-03-01 · 3 obs

● 2016-03-01 15:13:32
○ 2016-08-07 19:12:14
○ 2026-08-06 04:07:56

●NSada.ns.cloudflare.com2016-08-07 → 2026-08-06 · 3 obs

○ 2016-03-01 15:13:32
● 2016-08-07 19:12:14
● 2026-08-06 04:07:56

○NSdave.ns.cloudflare.com2016-03-01 → 2016-03-01 · 3 obs

● 2016-03-01 15:13:32
○ 2016-08-07 19:12:14
○ 2026-08-06 04:07:56

●NSeric.ns.cloudflare.com2016-08-07 → 2026-08-06 · 3 obs

○ 2016-03-01 15:13:32
● 2016-08-07 19:12:14
● 2026-08-06 04:07:56

○MXdc-d6d0aef9.technologypep.com2016-03-01 → 2016-03-01 · 3 obs

● 2016-03-01 15:13:32
○ 2016-08-07 19:12:14
○ 2026-08-06 04:07:56

●MXmx.yandex.net2016-08-07 → 2026-08-06 · 3 obs

○ 2016-03-01 15:13:32
● 2016-08-07 19:12:14
● 2026-08-06 04:07:56

●A104.21.20.2532026-02-20 → 2026-08-06 · 3 obs

○ 2017-03-14 00:43:14
● 2026-02-20 04:19:16
● 2026-08-06 04:07:56

○A104.25.206.222016-08-07 → 2017-03-14 · 5 obs

○ 2016-03-01 15:13:32
● 2016-08-07 19:12:14
● 2017-03-14 00:43:14
○ 2026-02-20 04:19:16
○ 2026-08-06 04:07:56

○A104.25.207.222016-08-07 → 2017-03-14 · 5 obs

○ 2016-03-01 15:13:32
● 2016-08-07 19:12:14
● 2017-03-14 00:43:14
○ 2026-02-20 04:19:16
○ 2026-08-06 04:07:56

○A104.27.174.832016-03-01 → 2016-03-01 · 3 obs

● 2016-03-01 15:13:32
○ 2016-08-07 19:12:14
○ 2026-08-06 04:07:56

○A104.27.175.832016-03-01 → 2016-03-01 · 3 obs

● 2016-03-01 15:13:32
○ 2016-08-07 19:12:14
○ 2026-08-06 04:07:56

●A172.67.195.632026-02-20 → 2026-08-06 · 3 obs

○ 2017-03-14 00:43:14
● 2026-02-20 04:19:16
● 2026-08-06 04:07:56

○A2400:cb00:2048:1::6819:ce162017-03-14 → 2017-03-14 · 4 obs

○ 2016-08-07 19:12:14
● 2017-03-14 00:43:14
○ 2026-02-20 04:19:16
○ 2026-08-06 04:07:56

○A2400:cb00:2048:1::6819:cf162017-03-14 → 2017-03-14 · 4 obs

○ 2016-08-07 19:12:14
● 2017-03-14 00:43:14
○ 2026-02-20 04:19:16
○ 2026-08-06 04:07:56

○A2606:4700:3030::ac43:c33f2026-02-20 → 2026-06-11 · 5 obs

○ 2017-03-14 00:43:14
● 2026-02-20 04:19:16
● 2026-06-11 06:59:36
○ 2026-07-05 06:43:38
○ 2026-08-06 04:07:56

○A2606:4700:3031::6815:14fd2026-02-20 → 2026-06-11 · 5 obs

○ 2017-03-14 00:43:14
● 2026-02-20 04:19:16
● 2026-06-11 06:59:36
○ 2026-07-05 06:43:38
○ 2026-08-06 04:07:56

●A2606:4700:3035::6815:14fd2026-07-05 → 2026-08-06 · 3 obs

○ 2026-06-11 06:59:36
● 2026-07-05 06:43:38
● 2026-08-06 04:07:56

●A2606:4700:3037::ac43:c33f2026-07-05 → 2026-08-06 · 3 obs

○ 2026-06-11 06:59:36
● 2026-07-05 06:43:38
● 2026-08-06 04:07:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
technologypep.com	eric.ns.cloudflare.com, ada.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.54

NS records: eric.ns.cloudflare.com, ada.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for technologypep.com (unsigned zone)

⏱️ Timing

Total: 137ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.20.253, 172.67.195.63`
AAAA	2	`2606:4700:3035::6815:14fd, 2606:4700:3037::ac43:c33f`
NS	2	`ada.ns.cloudflare.com, eric.ns.cloudflare.com`
MX	1	`mx.yandex.net (pri: 10)`
TXT	4	`ahrefs-site-verification_be0efdf2f3d9703, bm-site-verification=dc6bba7fc45386d4a1b...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ada.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (eric.ns.cloudflare.com, eric.ns.cloudflare.com, eric.ns.cloudflare.com...)

Analysis

IP Addresses

technologypep.com directs to four IP numbers, which are 104.21.20.253, 172.67.195.63, 2606:4700:3035::6815:14fd and 2606:4700:3037::ac43:c33f.

celikis.com.tr, analytics.selven.fr, tesd-177.keterak.ru plus two other host names have IP numbers in common with technologypep.com.

Name Servers

technologypep.com is served by two delegated name servers, ada.ns.cloudflare.com and eric.ns.cloudflare.com.

The name server configuration of technologypep.com is shared with other domains, for instance freshnrebel.fr, topvpnsoftware.com, leading-edge.marketing and two others.

There is at least partial name server overlap between technologypep.com and other domains — education-rybakov.pages.dev, ysssb.com, resultadodeltelekino.com and two more among them.

These name servers frequently co-occur with the name servers syeef.ns.cloudflare.com and pam.ns.cloudflare.com.

Hosts with 6 IP addresses each:

ada.ns.cloudflare.com carries IP addresses 108.162.192.54, 172.64.32.54 and 173.245.58.54, with 3 other addresses beyond those.

eric.ns.cloudflare.com carries IP addresses 108.162.193.112, 172.64.33.112 and 173.245.59.112, with 3 other addresses beyond those.

Mail Servers

technologypep.com uses one mail server — mx.yandex.net.

The mail server setup of technologypep.com matches that of other domains such as bissa-m.ru, otkritki2.ru, monumenti.ru and two others.

There is at least a partial overlap in mail servers between technologypep.com and other domains like cybermax.spb.ru, wisdomdentalsupply.com and nmsonline.ru.

mx.yandex.net carries two IP numbers: 77.88.21.249 and 2a02:6b8::311.