securityrfq.net - robtex.com
securityrfq.net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | amrns1501.accenture.com ⭐ | ||||||
| A | 170.252.248.5🇺🇸 ANSER_ADVISORY170.252.248.0/24 | ||||||
| PTR | amrns1501.accenture.com | ||||||
| NS | apans3501.accenture.com | ||||||
| A | 170.252.160.140🇵🇭 ANSER_ADVISORY170.252.160.0/24 | ||||||
| PTR | apans3501.accenture.com | ||||||
| NS | cfans1001.accenture.com | ||||||
| A | 162.159.8.127Cloudflare162.159.8.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | cfans1002.accenture.com | ||||||
| A | 162.159.9.58Cloudflare162.159.9.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | emens3501.accenture.com | ||||||
| A | 170.252.72.92🇪🇸 ANSER_ADVISORY170.252.72.0/21 Accenture Route Object | ||||||
| PTR | emens3501.accenture.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | amrns1501.accenture.comdnsadmin@accenture.com serial=4776 | ||||||
net
| 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.netnstld@verisign-grs.com serial=1771291465 | ||||||
Same first word
securityrfq.net |
DNS History
23 records (5 active, 18 former)
●NSamrns1501.accenture.com2026-02-23 → 2026-03-24 · 3 obs
○ 2017-02-12 06:31:46
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
●NSapans3501.accenture.com2026-02-23 → 2026-03-24 · 3 obs
○ 2017-02-12 06:31:46
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
●NScfans1001.accenture.com2026-02-23 → 2026-03-24 · 3 obs
○ 2017-02-12 06:31:46
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
●NScfans1002.accenture.com2026-02-23 → 2026-03-24 · 3 obs
○ 2017-02-12 06:31:46
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
●NSemens3501.accenture.com2026-02-23 → 2026-03-24 · 3 obs
○ 2017-02-12 06:31:46
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
● 2026-02-23 11:06:32
● 2026-03-24 11:05:12
○NSpdns1.ultradns.net2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSpdns2.ultradns.net2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSpdns3.ultradns.org2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSpdns4.ultradns.org2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSpdns5.ultradns.info2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSpdns6.ultradns.co.uk2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○NSudns1.ultradns.net2015-06-30 → 2017-02-12 · 4 obs
● 2015-06-30 22:53:54
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○NSudns2.ultradns.net2015-06-30 → 2017-02-12 · 4 obs
● 2015-06-30 22:53:54
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○MXexcu-mxib-1.symantec.com2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○MXextu-mxib-1.symantec.com2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○MXextu-mxib-2.symantec.com2015-06-30 → 2016-06-29 · 4 obs
● 2015-06-30 22:53:54
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
○ 2017-02-12 06:31:46
○ 2026-03-24 11:05:12
○MXtus1smtinbpex01.symantec.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○MXtus1smtinbpex02.symantec.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○MXtus1smtinbpex03.symantec.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○A155.64.16.512016-06-29 → 2017-02-12 · 5 obs
○ 2016-03-11 05:16:34
● 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○A155.64.49.542016-06-29 → 2017-02-12 · 5 obs
○ 2016-03-11 05:16:34
● 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
● 2016-06-29 10:50:44
● 2017-02-12 06:31:46
○ 2026-02-23 11:06:32
○ 2026-03-24 11:05:12
○A206.204.52.312015-06-30 → 2016-03-11 · 4 obs
● 2015-06-30 22:53:54
● 2016-03-11 05:16:34
○ 2016-06-29 10:50:44
○ 2026-03-24 11:05:12
● 2016-03-11 05:16:34
○ 2016-06-29 10:50:44
○ 2026-03-24 11:05:12
○A216.12.145.202015-06-30 → 2016-03-11 · 4 obs
● 2015-06-30 22:53:54
● 2016-03-11 05:16:34
○ 2016-06-29 10:50:44
○ 2026-03-24 11:05:12
● 2016-03-11 05:16:34
○ 2016-06-29 10:50:44
○ 2026-03-24 11:05:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| securityrfq.net | amrns1501.accenture.com, emens3501.accenture.com, apans3501.accenture.com, cfans1001.accenture.com... | - |
✅ Authoritative Response
Server:170.252.248.5
NS records: amrns1501.accenture.com, emens3501.accenture.com, apans3501.accenture.com, cfans1001.accenture.com, cfans1002.accenture.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1824ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 5 | amrns1501.accenture.com, cfans1002.accenture.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | amrns1501.accenture.com dnsadmin.accentu |
Analysis
Name Servers
securityrfq.net is delegated to five name servers: amrns1501.accenture.com, apans3501.accenture.com, cfans1001.accenture.com, cfans1002.accenture.com and emens3501.accenture.com.
securityrfq.net at least partially shares name servers with other domains, for instance theshelbygroup.info, bluehorseshoesummit.com, bvboard.net, accenture.berlin and froneribpo.com.br.
These name servers are commonly used alongside emens1901.accenture.com and amrns1501accenture.com.
Host names with one IP number:
amrns1501.accenture.com points to 170.252.248.5
apans3501.accenture.com points to 170.252.160.140
cfans1001.accenture.com points to 162.159.8.127
cfans1002.accenture.com points to 162.159.9.58
emens3501.accenture.com points to 170.252.72.92