Skip to content

Hostname

butikkene.no

Last fetched

butikkene.no resolves to 213.162.240.14, announced in 213.162.224.0/19 by ASN-EMPSECURE - EMP SECURE AS in NO. butikkene.no 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 · butikkene.noRouting diversity1.5/10Peering density4.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/butikkene.no

Resolution chain

IPv6 resolution

Attribution

emp secure

ORIGIN_AS

WHOIS identity

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

Subdomain
autodiscover.butikkene.no
cpanel.butikkene.no
cpcalendars.butikkene.no
cpcontacts.butikkene.no
mail.butikkene.no
webdisk.butikkene.no
webmail.butikkene.no
www.butikkene.no

Showing 8 of 8 subdomains (8 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

Sample outbound links

Mail and authentication

Nameservers

  • ns1.proisp.no
  • ns2.proisp.no

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • ip: 46.250.221.13/26
  • include: _spf.google.com
  • a: butikkene.no
  • ip: 213.162.240.14
  • ip: 46.250.221.30

Threat-feed evidence

History

Related pages

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