sweetffa.com - dns.ninja

sweetffa.com

DNSSEC⚠️ Not signed
NSa.misconfigured.powerdns.server ⭐
NSa.pipe.co
A46.20.238.100🇬🇧 IOMART-AS46.20.224.0/20 Melbourne Originated Routes
NSb.pipe.co
A159.89.249.145🇬🇧 DIGITALOCEAN159.89.248.0/22 DigitalOcean
MXmail.sweetffa.com ⭐
A185.252.161.177🇺🇸 FullFibre185.252.160.0/23
TXTv=spf1 mx a:mail.sweetffa.com ~all
SOAa.misconfigured.powerdns.serverhostmaster@sweetffa.com 2026-07-18 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1784730512

Subdomains

mail.sweetffa.com

Same first word

sweetffa.com

DNS History

20 records (4 active, 16 former)

20162017201820192020202120222023202420252026NSa.misconfigured.powerdns.servera.pipe.cob.pipe.cons1-01.azure-dns.comns1-08.azure-dns.comns2-01.azure-dns.netns2-08.azure-dns.netns3-01.azure-dns.orgns3-08.azure-dns.orgns4-01.azure-dns.infons4-08.azure-dns.infons5.nameserverservice.dens6.nameserverservice.deMXmail.sweetffa.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA62.75.187.149
●NSa.misconfigured.powerdns.server2026-02-16 → 2026-07-22 · 6 obs
○ 2017-07-23 05:24:20
● 2026-02-16 00:20:40
● 2026-06-03 03:23:00
○ 2026-06-07 05:30:26
● 2026-06-11 10:45:44
● 2026-07-22 14:50:52
●NSa.pipe.co2026-02-16 → 2026-07-22 · 3 obs
○ 2017-07-23 05:24:20
● 2026-02-16 00:20:40
● 2026-07-22 14:50:52
●NSb.pipe.co2026-02-16 → 2026-07-22 · 3 obs
○ 2017-07-23 05:24:20
● 2026-02-16 00:20:40
● 2026-07-22 14:50:52
○NSns1-01.azure-dns.com2016-07-11 → 2016-07-11 · 4 obs
○ 2016-03-16 03:26:22
● 2016-07-11 07:36:10
○ 2017-01-04 09:10:18
○ 2026-07-22 14:50:52
○NSns1-08.azure-dns.com2017-01-04 → 2017-07-23 · 5 obs
○ 2016-07-11 07:36:10
● 2017-01-04 09:10:18
● 2017-07-23 05:24:20
○ 2026-02-16 00:20:40
○ 2026-07-22 14:50:52
○NSns2-01.azure-dns.net2016-07-11 → 2016-07-11 · 4 obs
○ 2016-03-16 03:26:22
● 2016-07-11 07:36:10
○ 2017-01-04 09:10:18
○ 2026-07-22 14:50:52
○NSns2-08.azure-dns.net2017-01-04 → 2017-07-23 · 5 obs
○ 2016-07-11 07:36:10
● 2017-01-04 09:10:18
● 2017-07-23 05:24:20
○ 2026-02-16 00:20:40
○ 2026-07-22 14:50:52
○NSns3-01.azure-dns.org2016-07-11 → 2016-07-11 · 4 obs
○ 2016-03-16 03:26:22
● 2016-07-11 07:36:10
○ 2017-01-04 09:10:18
○ 2026-07-22 14:50:52
○NSns3-08.azure-dns.org2017-01-04 → 2017-07-23 · 5 obs
○ 2016-07-11 07:36:10
● 2017-01-04 09:10:18
● 2017-07-23 05:24:20
○ 2026-02-16 00:20:40
○ 2026-07-22 14:50:52
○NSns4-01.azure-dns.info2016-07-11 → 2016-07-11 · 4 obs
○ 2016-03-16 03:26:22
● 2016-07-11 07:36:10
○ 2017-01-04 09:10:18
○ 2026-07-22 14:50:52
○NSns4-08.azure-dns.info2017-01-04 → 2017-07-23 · 5 obs
○ 2016-07-11 07:36:10
● 2017-01-04 09:10:18
● 2017-07-23 05:24:20
○ 2026-02-16 00:20:40
○ 2026-07-22 14:50:52
○NSns5.nameserverservice.de2015-07-21 → 2016-03-16 · 4 obs
● 2015-07-21 02:20:04
● 2016-03-16 03:26:22
○ 2016-07-11 07:36:10
○ 2026-07-22 14:50:52
○NSns6.nameserverservice.de2015-07-21 → 2016-03-16 · 4 obs
● 2015-07-21 02:20:04
● 2016-03-16 03:26:22
○ 2016-07-11 07:36:10
○ 2026-07-22 14:50:52
○MXalt1.aspmx.l.google.com2026-02-16 → 2026-04-30 · 5 obs
○ 2016-07-11 07:36:10
● 2026-02-16 00:20:40
● 2026-04-30 09:18:30
○ 2026-05-03 08:49:08
○ 2026-07-22 14:50:52
○MXalt2.aspmx.l.google.com2026-02-16 → 2026-04-30 · 5 obs
○ 2016-07-11 07:36:10
● 2026-02-16 00:20:40
● 2026-04-30 09:18:30
○ 2026-05-03 08:49:08
○ 2026-07-22 14:50:52
○MXalt3.aspmx.l.google.com2026-02-16 → 2026-04-30 · 5 obs
○ 2016-07-11 07:36:10
● 2026-02-16 00:20:40
● 2026-04-30 09:18:30
○ 2026-05-03 08:49:08
○ 2026-07-22 14:50:52
○MXalt4.aspmx.l.google.com2026-02-16 → 2026-04-30 · 5 obs
○ 2016-07-11 07:36:10
● 2026-02-16 00:20:40
● 2026-04-30 09:18:30
○ 2026-05-03 08:49:08
○ 2026-07-22 14:50:52
○MXaspmx.l.google.com2026-02-16 → 2026-04-30 · 5 obs
○ 2016-07-11 07:36:10
● 2026-02-16 00:20:40
● 2026-04-30 09:18:30
○ 2026-05-03 08:49:08
○ 2026-07-22 14:50:52
●MXmail.sweetffa.com2015-07-21 → 2026-07-22 · 9 obs
● 2015-07-21 02:20:04
● 2016-03-16 03:26:22
○ 2016-07-11 07:36:10
○ 2026-04-30 09:18:30
● 2026-05-03 08:49:08
● 2026-06-03 03:23:00
○ 2026-06-07 05:30:26
● 2026-06-11 10:45:44
● 2026-07-22 14:50:52
○A62.75.187.1492015-07-21 → 2016-03-16 · 4 obs
● 2015-07-21 02:20:04
● 2016-03-16 03:26:22
○ 2016-07-11 07:36:10
○ 2026-07-22 14:50:52

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
sweetffa.coma.pipe.co, b.pipe.co-

✅ Authoritative Response

Server:46.20.238.100

NS records: a.pipe.co, b.pipe.co

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sweetffa.com (unsigned zone)

⏱️ Timing

Total: 672ms | Queries: -

📄 Records

TypeCountSample Data
NS2b.pipe.co, a.pipe.co
MX1mail.sweetffa.com (pri: 10)
TXT1v=spf1 mx a:mail.sweetffa.com ~all
SOA1a.misconfigured.powerdns.server hostmast

Analysis

Hierarchy

sweetffa.com serves as the parent of mail.sweetffa.com.

Name Servers

Three name servers are authoritative for sweetffa.com: a.pipe.co, b.pipe.co and a.misconfigured.powerdns.server.

sweetffa.com has at least partial name server overlap with other domains, such as 132.135.45.in-addr.arpa, asiangirlpics.com, klr1.net and two others.

ns1.ipbery.com, ns2.ipbery.com and ns1.rybatr.com — plus 6 other name servers — are commonly paired with these name servers.

a.pipe.co directs to 46.20.238.100 and b.pipe.co directs to 159.89.249.145; each host name points to exactly one IP number.

Mail Servers

sweetffa.com uses one mail server — mail.sweetffa.com.

sweetffa.com uses the same mail servers as other domains, including andymorrell.net.

There is one IP number for mail.sweetffa.com: 185.252.161.177.