Skip to content

Hostname

sera.com.np

Last fetched

sera.com.np resolves to 193.180.212.97, announced in 193.180.212.0/24 by WEBDOCK-AS - Webdock.io ApS in DK. sera.com.np 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 · sera.com.npRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.9/10canon.whisper.security/host/sera.com.np

Resolution chain

IPv6 resolution

No AAAA record for sera.com.np is recorded in WhisperGraph.

Attribution

webdock io

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for sera.com.np. 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

  • alexia.ns.cloudflare.com
  • andronicus.ns.cloudflare.com
  • ns1.himalayanhosting.com
  • ns2.himalayanhosting.com
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • s5642.lon1.stableserver.net

SPF policy

  • include: spf.mysecurecloudhost.com
  • a: sera.com.np
  • mx: sera.com.np
  • ip: 192.250.234.167
  • ip: 192.250.234.71

Threat-feed evidence

History

Related pages

Pivot from sera.com.np 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: "sera.com.np"})-[: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.