Skip to content

Hostname

secure4.me

Last fetched

secure4.me resolves to 213.202.255.102, announced in 213.204.245.0/24 by MYLOC-AS - WIIT AG in DE. secure4.me 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 · secure4.meRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint3.2/10canon.whisper.security/host/secure4.me

Resolution chain

IPv6 resolution

No AAAA record for secure4.me is recorded in WhisperGraph.

Attribution

myloc wiit

ORIGIN_AS

WHOIS identity

Registrar
iana:151
Registrant organisation
nextgen-networks

Subdomains

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns1.world4you.at
  • ns2.world4you.at

MX records

  • nextgen.email
  • host04.nextgen.email

SPF policy

  • a: nextgen.email
  • a: host04.nextgen.email
  • a: secure4.me
  • mx: secure4.me

Threat-feed evidence

History

Related pages

Pivot from secure4.me 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: "secure4.me"})-[: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.