Skip to content

Hostname

simple-surfing.com

Last fetched

simple-surfing.com resolves to 80.87.111.84, announced in 80.87.110.0/23 by INTERNET-PRO-AS - Internet-Pro LLC in RU. simple-surfing.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · simple-surfing.comRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/simple-surfing.com

Resolution chain

IPv6 resolution

No AAAA record for simple-surfing.com is recorded in WhisperGraph.

Attribution

pro

ORIGIN_AS

WHOIS identity

Registrar
iana:463
Registrant organisation
personal data, can not be publicly disclosed according to applicable laws.
Contact emails
3aa7a3fbf6884f30a1d6e4d7d882fce1.protect@whoisguard.com, 9904557783e244189f589d208e9900f5.protect@whoisguard.com, afa3cce88fee4062bea54265198ad090.protect@whoisguard.com, ber_detektiv@mail.ru

Subdomains

Subdomain
download.simple-surfing.com
mx0.simple-surfing.com
mx1.simple-surfing.com
oplata.simple-surfing.com
surfing.simple-surfing.com
www.simple-surfing.com

Showing 6 of 6 subdomains (6 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns1.netangels.ru
  • ns2.netangels.ru
  • ns3.netangels.ru
  • ns4.netangels.ru

MX records

  • mx0.simple-surfing.com
  • mx1.simple-surfing.com

SPF policy

  • a: simple-surfing.com
  • mx: simple-surfing.com
  • include: netangels.ru
  • include: _spf.yandex.ru
  • ip: 136.243.37.78
  • ip: 5.101.114.155

Threat-feed evidence

History

Related pages

Pivot from simple-surfing.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: "simple-surfing.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.