Hostname
bestsecure2020.com
Last fetched
bestsecure2020.com resolves to 103.224.212.215, announced in 103.224.212.0/24 by STEFANSTEVAN - Stefan Stevanovic in AU. bestsecure2020.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:25 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 23:27:23 GMT
Nutrition Label
Resolution chain
- 103.224.212.215
- 173.234.157.130
173.234.156.0/22 · LEASEWEB-USA-NYC - Leaseweb USA, Inc. · Edison, US
- 212.32.255.84
212.32.224.0/19 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 212.7.209.207
212.7.208.0/22 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 212.92.105.21
212.92.104.0/21 · NFORCE - NForce Entertainment B.V. · Roosendaal, NL
- 23.82.16.54
- 23.82.16.55
- 78.157.209.171
78.157.208.0/20 · UKSERVERS-AS - UK Dedicated Servers Limited · London, GB
- 78.157.209.173
78.157.208.0/20 · UKSERVERS-AS - UK Dedicated Servers Limited · London, GB
IPv6 resolution
No AAAA record for bestsecure2020.com is recorded in WhisperGraph.
Attribution
stefan stevanovic
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for bestsecure2020.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Mail and authentication
Nameservers
- ns1.abovedomains.com
- ns15.abovedomains.com
- ns16.abovedomains.com
- ns2.abovedomains.com
- ns1.emu-dns.com
- ns2.emu-dns.com
- ns1.hostresolver.com
- ns2.hostresolver.com
- ns1.milesmx.com
- ns2.milesmx.com
MX records
- park-mx.above.com
SPF policy
- ip: fdcf:abda:4154::/48
Threat-feed evidence
History
Related pages
Pivot from bestsecure2020.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bestsecure2020.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.