indexo.dev

gilmoreblog.com

.com crawl

First seen 2026-04-22 · Last seen 2026-05-12 · ok HTTP/1.1 200 3144 ms crawled 2026-05-16

US · 65.181.111.242 · AS14670 WHG Hosting Services Ltd

Reputation 89/100 weak security headers dmarc monitor-only

Classifying

HTML metadata

Title
Gilmore Restaurant Blog - The official blog of Gilmore Restaurants in Grand Rapids and West Michigan.
Description
The official blog of Gilmore Restaurants in Grand Rapids and West Michigan.
Language
en-US
Generator
WordPress 5.2.21
Canonical
http://gilmoreblog.com/
Feeds

Open Graph

url
http://gilmoreblog.com/
title
Gilmore Restaurant Blog - The official blog of Gilmore Restaurants in Grand Rapids and West Michigan.
locale
en_US
site name
Gilmore Restaurant Blog
description
The official blog of Gilmore Restaurants in Grand Rapids and West Michigan.

Technology

Server
LiteSpeed
CMS
WordPress
Fonts
  • Google Fonts
Third-party hosts loaded (8)
  • i0.wp.com×9
  • i1.wp.com×5
  • fonts.googleapis.com×3
  • i2.wp.com×2
  • s0.wp.com×2
  • gmpg.org×1
  • s.w.org×1
  • stats.wp.com×1

Social

Registration

Registrar
GoDaddy.com, LLC
Created
2018-02-08
Expires
2027-02-08 264 days left
Updated
2026-02-09
Name servers
  • ns41.hostforweb.net
  • ns42.hostforweb.net

DNS records live

NS
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
MX
  • 0 gilmoreblog.com

Email authentication partial

SPF
v=spf1 +a +mx +ip4:154.16.119.57 include:spf.antispamcloud.com +ip4:65.181.111.242 +include:relay.mailchannels.net +ip4:154.16.146.201 ~all
softfail (~all)
DMARC
v=DMARC1; p=none;
policy: none (monitoring only)
DKIM
  • default: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt+wcB4L0s2ADscg/uaq3tvIM5xXjd/rlzj4XJFvNIZLqKfaBz2OWa+ymnfjtZEjda93/OMgwdH9N2v…
selectors probed

Certificate (current)

R10
from 2024-06-19 to 2024-09-17
Expired 609 days ago

Full certificate history on crt.sh ↗

HTTP security headers

Header hygiene 35/100 Checked over plain HTTP: http://gilmoreblog.com/

findings
  • checked over plain HTTP
  • missing Content Security Policy
  • missing frame protection
  • missing content type protection
  • missing Referrer Policy
  • missing Permissions Policy

Links to (7)

Linked from (1)